TE-16.3 encap_frr_with_reencap_vrf_test.go#5443
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses a configuration issue in the gRIBI test suite where two distinct next hop operations were incorrectly sharing the same index. By assigning a unique index to the decap+encap operation, the test now correctly creates separate next hop entries as intended, preventing unintended updates to existing entries. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
2 participants
In subtest we supposed to create the above "decap+encap" and "lookup in default table" as two separate NHs using different IDs. But a recent script change made them use the same ID, creating a single NH with a subsequent update.